Map data processing unit

ABSTRACT

A map data processing unit includes a batch update section and dynamic update section. A type of update data fed from an update data input section is decided using header information. If the update data is route search data, the batch update section collectively updates all the map data to latest version map data according to the update data from the update data input section. If the update data is not the route search data, the dynamic update section updates the map data to the latest version map data according to the update data every time the map data becomes necessary. Thus performing the collective or dynamic update according to the type of the update data enables the update to the latest map data without affecting the operation speed of a navigation function, with minimizing the time precluding the use of the navigation function.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a map data processing unit capable ofupdating map data without affecting the operation speed of itsnavigation function with minimizing the time of precluding the use ofthe navigation function.

2. Description of Related Art

A conventional vehicle-mounted navigation system or the like usuallyoperates on map data stored in a recording medium such as a CD-ROM orDVD-ROM, and updates the map data by changing the CD-ROM or DVD-ROM. Themethod, however, cannot update the data frequently, only once or twice ayear at most, and hence it cannot always provide the latest map data.

In contrast with this, a method is proposed of updating the map data ina shorter period of time by storing the map data in a rewritable medium(refer to Relevant Reference 1, for example).

Relevant Reference 1: Japanese patent application laid-open No.2002-49624 (page 4, FIG. 7).

With such an arrangement, the conventional map data processing unitupdates the map data when it becomes necessary. Thus, when using aplurality of map data in processing such as route search, it imposes aheavy load on the navigation system, thereby presenting a problem ofretarding the operation.

In addition, carrying out the update processing of all the map data atonce offers a problem of precluding the use of the vehicle-mountednavigation because the update processing takes a lot of time. Forexample, to rewrite all the map data by reading data from a DVD-ROM,about nine gigabit data must be read. Since a current DVD-ROM driveusually reads about 1-2 MB per second, it takes about 1-2 hours to readthe map data, with precluding the use of the navigation during thattime.

SUMMARY OF THE INVENTION

The present invention is implemented to solve the foregoing problem. Itis therefore an object of the present invention to provide a map dataprocessing unit capable of updating the map data without affecting theoperation speed of its navigation function with minimizing the time ofdisabling the navigation function.

According to a first aspect of the present invention, there is provideda map data processing unit that has a function of updating map data, andincludes a display section for performing various types of displayincluding display of a processing result of the map data, a manipulationsection for carrying out input manipulation for processing the map data,and a control section for performing entire control, the map dataprocessing unit including: an update data input section for inputtingupdate data for updating the map data to latest version map data; abatch update section for collectively updating all the map data to thelatest version map data in accordance with the update data fed from theupdate data input section; a dynamic update section for updating the mapdata to the latest version map data in accordance with the update datafed from the update data input section every time the map data becomesnecessary; an update method selecting section for selecting one of thebatch update section and dynamic update section in response to theupdate data; and a map data storing section for storing the map data.

Thus, the map data processing unit can switch the update method betweenthe batch update and the dynamic update in response to the update data.As a result, it offers an advantage of being able to perform the updateto the latest version map data without affecting the operation speed ofthe navigation, with minimizing the time of precluding the use of thenavigation.

According to a second aspect of the present invention, there is provideda map data processing unit that has a function of updating map data, andincludes a display section for performing various types of displayincluding display of a processing result of the map data, a manipulationsection for carrying out input manipulation for processing the map data,and a control section for performing entire control, the map dataprocessing unit including: a post-update data cache section fortemporarily storing, in a cache, latest version map data to be read inresponse to a request for map data; an update data input section forinputting update data for updating the map data to the latest versionmap data, when the post-update data cache section does not store the mapdata; and a dynamic update section for updating, when the update datainput section inputs the update data, old version map data to latestversion map data to be stored in the cache, in accordance with theupdate data fed from the update data input section every time a requestfor the map data occurs.

Thus, the map data processing unit can utilize the latest version mapdata by only reading it from the cache using the post-update data cachesection, if the map data associated with the request from an applicationis stored in the cache by the post-update data cache section. As aresult, it offers an advantage of being able to reduce the time of thedynamic update processing.

According to a third aspect of the present invention, there is provideda map data processing unit including: an update data input section forinputting update data for updating old version map data to latestversion map data; an update data recording section for recording theupdate data input by the update data input section; an update sectionfor updating, when a map data request from an application occurs, theold version map data to the latest version map data in accordance withthe old version map data and the update data stored in the update datarecording section, which old version map data and update data correspondto the map data associated with the map data request from theapplication; a map data storing section for storing the map data; adisplay section for displaying a processing result of the map data; amanipulation section for performing input manipulation for processingthe map data; and a control section for carrying out overall control.

Thus, the map data processing unit offers an advantage of being able touse the update data input section for other purposes during thenavigation operation by inputting from the update data input section theupdate data for updating the map data associated with the request forthe map data from the application at a timing different from the timingduring the navigation operation, and by recording the update data intothe update data recording section.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a configuration of an embodiment 1 ofa map data processing unit in accordance with the present invention;

FIG. 2 is a flowchart illustrating the operation of an update methodselecting section of the embodiment 1 of the map data processing unit inaccordance with the present invention;

FIG. 3 is a flowchart illustrating the operation of a batch updatesection of the embodiment 1 of the map data processing unit inaccordance with the present-invention;

FIG. 4 is a flowchart illustrating the operation of a dynamic updatesection of the embodiment 1 of the map data processing unit inaccordance with the present invention;

FIG. 5 is a diagram illustrating a format of the map data stored in amap data storing section of the embodiment 1 of the map data processingunit in accordance with the present;

FIG. 6 is a diagram illustrating a format of the map data format storedin the map data storing section of the embodiment 1 of the map dataprocessing unit in accordance with the present invention;

FIG. 7 is a diagram illustrating a format of local data of theembodiment 1 of the map data processing unit in accordance with thepresent invention;

FIG. 8 is a diagram illustrating a format of differential update data ofthe embodiment 1 of the map data processing unit in accordance with thepresent invention;

FIG. 9 is a diagram illustrating a format of update data of theembodiment 1 of the map data processing unit in accordance with thepresent invention;

FIG. 10 is a flowchart illustrating the operation of the batch updatesection of an embodiment 2 of the map data processing unit in accordancewith the present invention;

FIG. 11 is a flowchart illustrating the operation of the batch updatesection of an embodiment 3 of the map data processing unit in accordancewith the present invention;

FIG. 12 is a flowchart illustrating the operation of the dynamic updatesection of the embodiment 3 of the map data processing unit inaccordance with the present invention;

FIG. 13 is a block diagram showing a configuration of an embodiment 4 ofthe map data processing unit in accordance with the present invention;

FIG. 14 is a flowchart illustrating the update operation of the map databy a differential data update section in the embodiment 4 of the mapdata processing unit in accordance with the present invention;

FIG. 15 is a flowchart illustrating the update operation of the map databy the differential data update section in an embodiment 5 of the mapdata processing unit in accordance with the present invention;

FIG. 16 is a block diagram showing a configuration of an embodiment 6 ofthe map data processing unit in accordance with the present invention;

FIG. 17 is a flowchart illustrating the update operation of the map databy a post-update data cache section in the embodiment 6 of the map dataprocessing unit in accordance with the present invention;

FIG. 18 is a block diagram showing a configuration of an embodiment 7 ofthe map data processing unit in accordance with the present invention;

FIG. 19 is a block diagram showing a configuration of an embodiment 8 ofthe map data processing unit in accordance with the present invention;

FIG. 20 is a block diagram showing a configuration of an embodiment 9 ofthe map data processing unit in accordance with the present invention;

FIG. 21 is a flowchart illustrating the update operation of the map databy a current position acquisition section of the embodiment 9 of the mapdata processing unit in accordance with the present invention;

FIG. 22 is a block diagram showing a configuration of an embodiment 10of the map data processing unit in accordance with the presentinvention;

FIG. 23 is a flowchart illustrating the update operation of the map databy the current position acquisition section and pre-update section inthe embodiment 10 of the map data processing unit in accordance with thepresent invention;

FIG. 24 is a block diagram showing a configuration of an embodiment 11of the map data processing unit in accordance with the presentinvention;

FIG. 25 is a flowchart illustrating the update operation of the map datausing a location registration section and post-update data cache sectionof the embodiment 11 of the map data processing unit in accordance withthe present invention;

FIG. 26 is a block diagram showing a configuration of an embodiment 12of the map data processing unit in accordance with the presentinvention;

FIG. 27 is a flowchart illustrating the update operation of the map datausing the location registration section and pre-update data recordingsection of the embodiment 12 of the map data processing unit inaccordance with the present invention;

FIG. 28 is a block diagram showing a configuration of an embodiment 13of the map data processing unit in accordance with the presentinvention;

FIG. 29 is a flowchart illustrating the update operation of the map datausing a driving history storing section and post-update data cachesection of the embodiment 13 of the map data processing unit inaccordance with the present invention;

FIG. 30 is a block diagram showing a configuration of an embodiment 14of the map data processing unit in accordance with the presentinvention;

FIG. 31 is a flowchart illustrating the update operation of the map datausing the driving history storing section and pre-update section of theembodiment 14 of the map data processing unit in accordance with thepresent invention;

FIG. 32 is a block diagram showing a configuration of an embodiment 15of the map data processing unit in accordance with the presentinvention;

FIG. 33 is a flowchart illustrating the update data recording operationinto the update data recording section of the embodiment 15 of the mapdata processing unit in accordance with the present invention; and

FIG. 34 is a flowchart illustrating the update operation of the map databy the dynamic update section of the embodiment 15 of the map dataprocessing unit in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The invention will now be described with reference to the accompanyingdrawings.

Embodiment 1

FIG. 1 is a block diagram showing a configuration of an embodiment 1 ofthe map data processing unit. It comprises a map data storing section101 for storing map data; an update data input section 102 for inputtingupdate data; a batch update section 103 for collectively updating themap data stored in the map data storing section 101 using one or moreupdate data input via the update data input section 102; a dynamicupdate section 104 for updating the map data stored in the map datastoring section 101 using one or more update data input via the updatedata input section 102 when necessary; an update method selectingsection 105 for selecting one of the batch update section 103 anddynamic update section 104 in response to differential data; a displaysection 106 for carrying out display based on the map data; amanipulation section 107 for carrying out various manipulations; and acontrol section 108 for controlling the entire system.

The map data storing section 101 for storing the map data consists of arewritable medium such as a hard disk for storing the map data afterupdate. The update data input section 102 for inputting the update dataconsists of a data storing medium such as a CD-ROM, DVD-ROM or memorycard. The batch update section 103 collectively updates the map datastored in the map data storing section 101 using one or more update datasupplied from the update data input section 102. The dynamic updatesection 104 updates the map data stored in the map data storing section101 using one or more update data supplied from the update data inputsection 102 as needed. The update method selecting section 105 selectsone of the batch update section 103 and dynamic update section 104 inresponse to the update data. The display section 106 carries out thedisplay in accordance with the map data.

FIG. 5 is a diagram illustrating a format of the map data stored in themap data storing section 101; and FIG. 6 is a diagram illustrating aformat of a map data file stored in the map data storing section 101.

The map data consists of files, each of which includes one type of data.Each file contains header information and a plurality of local data(data #0-data #n). The header information consists of a data type, dataversion, file size and the number of the data as illustrated in FIG. 6.The data type indicates whether the data is used for map display, forlocation, for route search or for route guidance corresponding to theindividual functions of the navigation system.

The local data refers to data on individual regions obtained by dividingthe entire area. For example, data on whole Japan as illustrated in FIG.5 correspond to the entire map data file as illustrated in FIG. 6, andthe individual areas indicated by a mesh in FIG. 5 correspond to localdata (local data #0-#n).

FIG. 7 is a diagram illustrating formats of the local data. FIG. 7(a)illustrates a format of the local data used for map display. It includesthe data size of the local data; the data range of the local data; anddata actually used for the map display such as road line coordinatestrings representing geometry of roads, background line coordinatestrings representing geometry of rivers, railroads and the like, displaycharacter strings for displaying place names and the like, and displaysymbols for representing entities such as a school and hospital. FIG.7(b) illustrates a format of the local data for route search. Itincludes the data size of the local data; the data range of the localdata; node data mainly representing intersections; link datarepresenting the road data, and traffic regulation data.

As for the update data input via the update data input section 102 asshown in FIG. 1, there are two types of data: a complete set of updatedata for replacing the old map data; and differential update data forcarrying out the update in accordance with the difference between theold version and latest version of the map data. The format of thecomplete set of update data is the same as that of the map dataillustrated in FIGS. 5 and 6.

FIG. 8 is a diagram illustrating a format of the differential updatedata. Just as the map data, the differential update data consists offiles, each of which includes one type of data. Each file containsheader information and a plurality of update data #0-#n. The update data#0-#n correspond to the local data #0-#n as illustrated in FIG. 6.

The header information consists of information items indicating a datatype, a corresponding data version, a post-update data version, a filesize and the number of the update data. The data type corresponds to thedata type of the map data of FIG. 6. The corresponding data versionindicates the version of the map data to be updated. For example, whenthe corresponding data version is version 1.0, and the post-update dataversion is version 1.1, the differential update data is the data forupdating the map data of version 1.0 to the map data of version 1.1.

FIG. 9 is a diagram illustrating a format of the update data consistingof a data size indicating the size of the update data itself, apost-update data size indicating the size of the map data after theupdate, and the body of the update data for carrying out the map update.

Next, the operation of the present embodiment 1 will be described.

FIG. 2 is a flowchart illustrating the operation of the update methodselecting section 105 in the embodiment 1 of the map data processingunit. FIG. 3 is a flowchart illustrating the operation of the batchupdate section 103, and FIG. 4 is a flowchart illustrating the operationof the dynamic update section 104.

First, the operation of the update method selecting section 105 will bedescribed with reference to the flowchart of FIG. 2. The update methodselecting section 105 acquires header information of the update datafrom the update data input section 102 at step ST1201. Subsequently, theupdate method selecting section 105 decides the data type of the headerinformation at step ST1202. If it is the data for route search, theupdate method selecting section 105 has the batch update section 103carry out the batch update at step ST1203. If the data is not the datafor route search, the update method selecting section 105 registers thedata as the data to be subjected to the dynamic update at step ST1204.Finally, the update method selecting section 105 makes a decision as towhether the header information of all the data has been input at stepST1205, and terminates the processing if the input has been completed.Otherwise, the update method selecting section 105 repeats theprocessing from step ST1201.

Next, the operation of the batch update section 103 will be describedwith reference to FIG. 3.

The batch update section 103 deletes the map data to be updated at stepST1401, and records the corresponding complete set of update data in themap data storing section 101 at step ST1402. Then, the batch updatesection 103 changes the file name of the complete set of update data tothat of the deleted map data at step ST1403.

Next, the operation of the dynamic update section 104 will be describedwith reference to FIG. 4.

In response to a request for map data from the application at stepST1301, the dynamic update section 104 reads the map data from the mapdata storing section 101 at step ST1302. Then, the dynamic updatesection 104 makes a decision as to whether the data to be subjected tothe dynamic update corresponding to the read map data is present or notat step ST1303. If the data is not present, the dynamic update section104 terminates the processing. Otherwise, the dynamic update section 104acquires the corresponding update data at step ST1304, and updates themap at step ST1305.

Thus, the batch update section 103 updates the set of data for routesearch to the latest version map data, and records the latest versionmap data in the map data storing section 101. On the other hand, thedynamic update section 104 updates each of the remaining data every timethe application requires it.

The processing time of FIG. 3 is nearly the read time of the completeset of update data, which corresponds to the size of the map data forroute search of about several tens of megabytes. Thus, the processingcan be completed in several tens of seconds in the case of reading thedata from the DVD-ROM.

Although the foregoing description is made by way of example in whichthe data for route search is subjected to the batch update processing,data other than the route search data, which are considered to be rathersmall in size, can be used as the data to be subjected to the batchupdate processing.

In addition, although the target data to be subjected to the batchupdate processing is decided according to the data type, this is notessential. For example, the target data to be subjected to the batchupdate processing can be decided according to the data size rather thanthe data type.

Furthermore, although the update data input section 102 is assumed to bea data storing medium, this is not essential. For example, the updatedata can be input via various types of communication means such as amobile phone, DSRC (Dedicated Short Range Communication), Bluetooth, andwireless LAN.

As described above, the present embodiment 1 makes a decision as to theprocessing time and storage capacity required for carrying out the batchupdate processing from the map data type, map data size and the like;selects the data to be subjected the batch update; carries out the batchupdate processing; and carries out the dynamic update processing of theremaining data as needed. Thus, the present embodiment 1 offers anadvantage of being able to provide a map data processing unit capable ofupdating to the latest map data without affecting the operation speed ofthe navigation function, with minimizing the time of disabling thenavigation function.

Embodiment 2

FIG. 10 is a flowchart illustrating the operation of the batch updatesection of the present embodiment 2 of the map data processing unit. Theconfiguration of the map data processing unit to which the batch updatesection of the present embodiment 2 is applied is the same as that ofFIG. 1.

Referring to FIG. 10, the operation of the batch update section of themap data processing unit will be described.

The batch update section moves the map data to be updated to anotherdirectory to keep the map data before the update at step ST1501. Itrecords the corresponding complete set of update data into the map datastoring section 101 at step ST1502, and changes the file name of thecomplete set of update data at step ST1503.

Thus, the present embodiment 2 keeps the map data before the update.Accordingly, it offers an advantage of being able to recover the statebefore the update with ease, and hence to provide the map dataprocessing unit capable of carrying out the navigation using the mapdata of the previous version.

Embodiment 3

FIG. 11 is a flowchart illustrating the operation of the batch updatesection of the present embodiment 3 of the map data processing unit; andFIG. 12 is a flowchart illustrating the operation of its dynamic updatesection. The configuration of the map data processing unit to which thebatch update section and dynamic update section of the presentembodiment 3 are applied is the same as that of FIG. 1.

Referring to the flowchart of FIGS. 11 and 12, the operation of thepresent embodiment 3 will be described.

First, the operation of the batch update section 103 will be describedwith reference to FIG. 11. The batch update section 103 clears a batchupdate completion flag at step ST3001 to indicate that the batch updatehas not yet been completed. Then, the batch update section 103 recordsthe corresponding complete set of update data in the map data storingsection 101 at step ST3002, and displays a batch update preparationcompletion telop on the display section 106 shown in FIG. 1 at stepST3003. Subsequently, the batch update section 103 deletes the map dataat step ST3004, and changes the file name of the complete set of updatedata for the batch update to the file name of the deleted map data atstep ST3005. Finally, the batch update section 103 sets the batch updatecompletion flag at step ST3006 to indicate that the batch update hasbeen completed.

Next, the operation of the dynamic update section 104 will be describedwith reference to FIG. 12.

In response to a map data request from an application at step ST3101,the dynamic update section 104 reads the appropriate map data from themap data storing section 101 at step ST3102. Then, the dynamic updatesection 104 checks the batch update completion flag to decide as towhether the batch update completion flag has been cleared or not at stepST3103. If it has been cleared, and hence indicates that the batchupdate has not yet been completed, the dynamic update section 104terminates the dynamic update processing. As a result, the navigation isavailable using the old version map data read from the map data storingsection 101 in response to the map data request from the applicationeven during the batch update. On the other hand, if the batch updatecompletion flag has been set, and hence indicates that the batch updatehas been completed, the dynamic update section 104 makes a decision asto whether the data to be subjected to the dynamic update correspondingto the map data read from the map data storing section 101 is present ornot at step ST3104. If it is not present, the dynamic update section 104terminates the dynamic update processing. In contrast, if it is present,the dynamic update section 104 acquires the corresponding update data atstep ST3105, and updates the map in accordance with the dynamic updateprocessing at step ST3106.

As described above, the present embodiment 3 can read, in response tothe map data request from the application, the old version map data fromthe map data storing section 101 even during the batch update processingthat continues until the batch update is completed and the batch updatecompletion flag is set, thereby making available the navigation usingthe old version map data. Thus, the present embodiment 3 offers anadvantage of being able to provide the map data processing unit capableof increasing the convenience of users.

Embodiment 4

FIG. 13 is a block diagram showing a configuration of the presentembodiment 4 of the map data processing unit. In FIG. 13, the same orlike portions to those of FIG. 1 are designated by the same referencenumerals, and their description is omitted here.

In the present embodiment 4 of the map data processing unit, the batchupdate section 103 comprises a differential data update section 201 andan entire data update section 202.

The differential data update section 201 carries out the map update inaccordance with the differential data between the old version and latestversion map data. In contrast, the entire data update section 202carries out the map update by rewriting the old complete set of map datato the latest version map data in accordance with the corresponding newcomplete set of update data.

FIG. 14 is a flowchart illustrating the update operation of the map databy the differential data update section 201. On the other hand, the flowof the update operation of the map data by the entire data updatesection 202 is given by FIG. 3 described in connection with theforegoing embodiment 1.

Referring to FIG. 14, the map update operation by the differential dataupdate section 201 will be described.

First, the differential data update section 201 reads the old versionmap data recorded in the map data storing section 101 at step ST1601.Second, the differential data update section 201 acquires thecorresponding differential update data from the update data inputsection 102 at step ST1602, and updates the map in accordance with theold version map data and differential update data at step ST1603. Then,the differential data update section 201 records the post-update mapdata in the map data storing section 101 at step ST1604.

Subsequently, the differential data update section 201 makes a decisionas to whether all the data have been updated or not at step ST1605. Ifthe map data that has not yet been updated is left, the differentialdata update section 201 repeats the processing from step ST1601. Incontrast, if it completes the update of all the map data, thedifferential data update section 201 deletes the map data before theupdate at step ST1606. Then, the differential data update section 201changes the file name of the map data after the update to that of themap data before the update at step ST1607.

As described above, the present embodiment 4 enables the batch updateusing the complete set of update data or the differential update data.Thus, it offers an advantage of being able to provide the map dataprocessing unit capable of reducing the amount of the update data.

Embodiment 5

In the present embodiment 5 of the map data processing unit, the batchupdate section 103 has also the differential data update section andentire data update section as in the embodiment 4 of the map dataprocessing unit. The entire data update section updates the map datajust as that of the foregoing embodiment 4. However, the differentialdata update section updates the map data in a different manner. FIG. 15is a flowchart illustrating the update operation of the map data by thedifferential data update section.

Referring to FIG. 15, the update operation of the map data by thedifferential data update section of the present embodiment 5 will bedescribed.

The differential data update section reads the map data recorded in themap data storing section 101 at step ST1701, and acquires thedifferential update data from the update data input section 102 at stepST1702. Then, the differential data update section updates the map atstep ST1703, and records the map data after the update in the map datastoring section 101 at step ST1704. Subsequently, the differential dataupdate section makes a decision as to whether it updates all the data atstep ST1705. If the map data that has not yet been updated is left, thedifferential data update section repeats the processing from stepST1701. If the update of all the map data has been completed, thedifferential data update section moves the map data before the update toanother directory at step ST1706, and changes the file name of the mapdata after the update at step ST1707.

Thus, the present embodiment 5 stores the map data before the update tothe separate directory. Accordingly, it offers an advantage of beingable to provide the map data processing unit capable of recovering thestate before the update with ease.

In addition, the present embodiment 5 can carry out the batch update byusing either the complete set of update data or the differential updatedata. Thus, it offers an advantage of being able to provide the map dataprocessing unit capable of reducing the amount of the update data byusing the differential update data.

Embodiment 6

FIG. 16 is a block diagram showing a configuration of the presentembodiment 6 of the map data processing unit. In FIG. 16, the same orlike portions to those of FIG. 1 are designated by the same referencenumerals, and their description is omitted here. The present embodiment6 of the map data processing unit comprises a post-update data cachesection 301 for caching the map data updated by the dynamic updatesection 104, and a deletion data decision section 302 for deciding mapdata to be deleted among the map data cached.

FIG. 17 is a flowchart illustrating the update operation of the map datausing the post-update data cache section 301 in the embodiment 6 of themap data processing unit.

Referring to the flowchart of FIG. 17, the operation will be described.

When a request for map data is delivered from an application at stepST1801, the control section 108 makes a decision as to whether therequested map data is present in the cache or not at step ST1802. If themap data is present in the cache, the control section 108 reads theappropriate map data from the cache at step ST1803. Then, after updatingthe access history of the cache at step ST1804, the control section 108terminates the processing. In contrast, if the map data is not presentin the cache, the control section 108 reads the appropriate map datafrom the map data storing section 101 at step ST1805, and acquires thecorresponding differential update data from the update data inputsection 102 at step ST1806. Then, the control section 108 has thedynamic update section 104 update the map at step ST1807. Subsequently,the control section 108 makes a decision as to whether the cache hasavailable space or not at step ST1808. If it has no available space, thecontrol section 108 deletes the oldest map data in the access historyfrom the cache at step ST1809. In contrast, if the cache includesavailable space, or after deleting the oldest map data in the accesshistory from the cache, the control section 108 writes the updated mapdata into the cache at step ST1810. Finally, after setting the accesshistory at step ST1811, the control section 108 terminates theprocessing.

As described above, the present embodiment 6 includes the post-updatedata cache section 301. Accordingly, if the post-update data cachesection 301 includes the map data requested from the application, thepresent embodiment 6 can utilize the map data of the latest version byonly reading the map data by the post-update data cache section 301.Consequently, the present embodiment 6 offers an advantage of being ableto provide the map data processing unit capable of reducing the time ofthe dynamic update processing.

Embodiment 7

FIG. 18 is a block diagram showing a configuration of the presentembodiment 7 of the map data processing unit. In FIG. 18, the same orlike portions to those of FIG. 16 are designated by the same referencenumerals, and their description is omitted here. The present embodiment7 of the map data processing unit comprises a pre-update section 401 forcarrying out map update beforehand, and a pre-update data decisionsection 402 for deciding the map data to be updated by the pre-updatesection 401 beforehand.

According to the present embodiment 7, the pre-update data decisionsection 402 decides the map data to be updated by the pre-update section401 beforehand, and the pre-update section 401 carries out the mapupdate beforehand and stores the map data into the post-update datacache in advance. Accordingly, the present embodiment 7 offers anadvantage of being able to provide a map data processing unit capable ofreducing the time of the dynamic update processing of the map data usedat a high frequency by storing the highly used map data in thepost-update data cache.

Embodiment 8

FIG. 19 is a block diagram showing a configuration of the presentembodiment 8 of the map data processing unit. In FIG. 19, the same orlike portions to those of FIG. 18 are designated by the same referencenumerals, and their description is omitted here. The present embodiment8 of the map data processing unit comprises a pre-update data recordingsection 501 for recording the map data updated by the pre-update section401 in advance. According to the present embodiment 8, the pre-updatedata recording section 501 stores the map data updated in advance.Consequently, if the stored map data is the map data used at highfrequency, the present embodiment 8 offers an advantage of being able toprovide a map data processing unit capable of reducing the time of thedynamic update processing of the highly used map data.

Embodiment 9

FIG. 20 is a block diagram showing a configuration of the presentembodiment 9 of the map data processing unit. In FIG. 20, the same orlike portions to those of FIG. 18 are designated by the same referencenumerals, and their description is omitted here. The present embodiment9 of the map data processing unit comprises a current positionacquisition section 601 for detecting the position of a vehicle itbelongs to.

FIG. 21 is a flowchart illustrating the update operation of the map databy using the current position acquisition section 601 in the embodiment9 of the map data processing unit.

Referring to the flowchart of FIG. 21, the operation will be described.

First, the pre-update section 401 acquires the current position from thecurrent position acquisition section 601 at step ST1901. Second, thepre-update section 401 reads the map data around the current positionfrom the map data storing section 101 at step ST1902, and acquires thedifferential update data corresponding to the map data from the updatedata input section 102 at step ST1903. Then, the pre-update section 401updates the map at step ST1904. Subsequently, the pre-update section 401has the post-update data cache section 301 write the updated map datainto the cache at step ST1905, and sets the access history at stepST1906. Finally, the pre-update section 401 makes a decision as towhether all the surrounding maps have been read at step ST1907, andterminates the processing if all the maps have been read. If there issome map data left, the pre-update section 401 repeats the processingfrom step ST1902.

According to the present embodiment 9, the post-update data cache storesthe update data around the position of the vehicle (current position).Thus, the present embodiment 9 offers an advantage of being able toprovide a map data processing unit capable of reducing the time of thedynamic update processing of the map data around the position of thevehicle, which is used at high frequency.

Embodiment 10

FIG. 22 is a block diagram showing a configuration of the presentembodiment 10 of the map data processing unit. In FIG. 22, the same orlike portions to those of FIG. 20 are designated by the same referencenumerals, and their description is omitted here.

The present embodiment 10 of the map data processing unit comprises apre-update data recording section 501. The pre-update data recordingsection 501 stores the map data updated by the pre-update section 401 inadvance.

FIG. 23 is a flowchart illustrating the update operation of the map databy using the current position acquisition section 601 and pre-updatesection 401 in the embodiment 10 of the map data processing unit.

Referring to the flowchart of FIG. 23, the operation will be described.

First, the pre-update section 401 acquires the current position from thecurrent position acquisition section 601 at step ST2001. Subsequently,the pre-update section 401 reads the map data around the currentposition from the map data storing section 101 at step ST2002, andacquires the corresponding differential update data from the update datainput section 102 at step ST2003, followed by updating the map at stepST2004. Then, the pre-update section 401 writes the map data updated inadvance into the pre-update data recording section 501 at step ST2005,and makes a decision as to whether all the surrounding maps have beenread at step ST2006. If all the surrounding maps have been read, thepre-update section 401 terminates the processing. In contrast, when themap data that has not yet been read is left, the pre-update section 401repeats the processing from step ST2002.

According to the present embodiment 10, the pre-update data recordingsection 501 stores the map data updated in advance by the pre-updatesection 401. Thus, the present embodiment 10 offers an advantage ofbeing able to provide a map data processing unit capable of reducing thetime of the dynamic update processing of the map data around theposition of the vehicle, which is used at high frequency.

Embodiment 11

FIG. 24 is a block diagram showing a configuration of the presentembodiment 11 of the map data processing unit. In FIG. 24, the same orlike portions to those of FIG. 18 are designated by the same referencenumerals, and their description is omitted here.

The present embodiment 11 of the map data processing unit comprises alocation registration section 801 for carrying out locationregistration.

Next, the operation of the present embodiment 11 will be described.

FIG. 25 is a flowchart illustrating the update operation of the map datausing the location registration section 801 and post-update data cachesection 301 of the embodiment 11 of the map data processing unit.Referring to the flowchart of FIG. 25, the operation will be described.

First, the pre-update section 401 acquires a registration position fromthe location registration section 801 at step ST2101.

Subsequently, the pre-update section 401 reads the map data around theregistration position from the map data storing section 101 at stepST2102, and acquires the corresponding differential update data from theupdate data input section 102 at step ST2103, followed by updating themap at step ST2104.

Then, the pre-update section 401 has the post-update data cache section301 write the updated map data into the cache at step ST2105, and setsthe access history at step ST2106. Subsequently, the pre-update section401 makes a decision as to whether all the surrounding maps have beenread or not at step ST2107. If all the surrounding maps have been read,the pre-update section 401 terminates the processing. If there is somemap data left, the pre-update section 401 repeats the processing fromstep ST2102.

According to the present embodiment 11, the post-update data cachestores the update data around the registration position. Thus, thepresent embodiment 11 offers an advantage of being able to provide a mapdata processing unit capable of reducing the time of the dynamic updateprocessing of the map data around the registration location, which isused at high frequency.

Embodiment 12

FIG. 26 is a block diagram showing a configuration of the presentembodiment 12 of the map data processing unit. In FIG. 26, the same orlike portions to those of FIG. 24 are designated by the same referencenumerals, and their description is omitted here.

The present embodiment 12 of the map data processing unit comprises apre-update data recording section 501 which is not installed in theforegoing embodiment 11. The pre-update data recording section 501stores the map data updated by the pre-update section 401 in advance asdescribed above in the foregoing embodiment 10.

FIG. 27 is a flowchart illustrating the update operation of the map databy using the location registration section 801 and pre-update datarecording section 501 in the embodiment 12 of the map data processingunit. Referring to the flowchart of FIG. 27, the operation will bedescribed.

First, the pre-update section 401 acquires the registration positionfrom the location registration section 801 at step ST2201. Subsequently,the pre-update section 401 reads the map data around registrationposition from the map data storing section 101 at step ST2202, andacquires the corresponding differential update data from the update datainput section 102 at step ST2203, followed by updating the map at stepST2204. Then, the pre-update section 401 writes the updated map datainto the pre-update data recording section 501 at step ST2205, and makesa decision as to whether all the surrounding maps have been read at stepST2206. If all the surrounding maps have been read, the pre-updatesection 401 terminates the processing. In contrast, when the map datathat has not yet been read is left, the pre-update section 401 repeatsthe processing from step ST2202.

According to the present embodiment 12, the pre-update data recordingsection 501 stores the map data around the registration position. Thus,the present embodiment 12 offers an advantage of being able to provide amap data processing unit capable of reducing the time of the dynamicupdate processing of the map data around the registration location whichis used at high frequency.

Embodiment 13

FIG. 28 is a block diagram showing a configuration of the presentembodiment 13 of the map data processing unit. In FIG. 28, the same orlike portions to those of FIG. 18 are designated by the same referencenumerals, and their description is omitted here. The present embodiment28 of the map data processing unit comprises a driving history storingsection 1001 for storing driving history.

Next, the operation of the present embodiment 13 will be described.

FIG. 29 is a flowchart illustrating the update operation of the map databy using the driving history storing section 1001 and post-update datacache section 301 in the embodiment 13 of the map data processing unit.Referring to the flowchart of FIG. 29, the operation will be described.

First, the pre-update section 401 acquires the driving history positionfrom the driving history storing section 1001 at step ST2301. Then, thepre-update section 401 reads the map data around the driving historyposition from the map data storing section 101 at step ST2302, andacquires the corresponding differential update data from the update datainput section 102 at step ST2303, followed by updating the map at stepST2304. Subsequently, the pre-update section 401 has the post-updatedata cache section 301 write the updated map data into the cache at stepST2305, and sets the access history at step ST2306. Finally, thepre-update section 401 makes a decision as to whether all thesurrounding maps have been read or not at step ST2307. If all the mapshave been read, the pre-update section 401 terminates the processing. Ifthere is some map data left, the pre-update section 401 repeats theprocessing from step ST2302.

According to the present embodiment 13, the post-update data cachestores the updated map data around the driving history position. Thus,the present embodiment 13 offers an advantage of being able to provide amap data processing unit capable of reducing the time of the dynamicupdate processing of the map data around the driving history positionwhich is used at high frequency.

Embodiment 14

FIG. 30 is a block diagram showing a configuration of the presentembodiment 14 of the map data processing unit. The present embodiment 14of map data processing unit comprises the pre-update data recordingsection 501 the foregoing embodiment 13 of the map data processing unitlacks. As described above in connection with the foregoing embodiment12, the pre-update data recording section 501 records the map dataupdated by the pre-update section 401 in advance. In FIG. 30, since theremaining configuration is the same as that of the foregoing embodiment13 of map data processing unit, their description is omitted here bydesignating the same or like portions to those of FIG. 28 by the samereference numerals.

Next, the operation of the present embodiment 14 will be described.

FIG. 31 is a flowchart illustrating the update operation of the map databy using the driving history storing section 1001 and pre-update section401 in the present embodiment 14 of the map data processing unit.Referring to the flowchart of FIG. 31, the operation will be described.

First, the pre-update section 401 acquires the driving history positionfrom the driving history storing section 1001 at step ST2401. Second,the pre-update section 401 reads the map data around the driving historyposition from the map data storing section 101 at step ST2402, acquiresthe corresponding differential update data from the update data inputsection 102 at step ST2403, and updates the map at step ST2404. Then,the pre-update section 401 writes the updated map data into thepre-update data recording section 501 at step ST2405. Finally, thepre-update section 401 makes a decision as to whether all thesurrounding maps have been read at step ST2406. If all the maps havebeen read, the pre-update section 401 terminates the processing. Ifthere is some map data left, the pre-update section 401 repeats theprocessing from step ST2402.

Incidentally, as the driving history, it is possible to use not onlycoordinates of places passed by in actual drives, but also coordinatesof destinations or places on a route which are set in route search, orcoordinates of places of a search route.

As described above, according to the present embodiment 14, thepre-update data recording section 501 stores the map data updated byusing the map data around the driving history position and thecorresponding differential update data. Thus, the present embodiment 14offers an advantage of being able to provide a map data processing unitcapable of reducing the time of the dynamic update processing of the mapdata around the driving history position, which is used at highfrequency.

Embodiment 15

FIG. 32 is a block diagram showing a configuration of the presentembodiment 15 of the map data processing unit. In FIG. 32, the same orlike portions to those of FIG. 1 are designated by the same referencenumerals, and their description is omitted here. The present embodiment15 of the map data processing unit comprises an update data recordingsection 3201 for recording the update data fed from the update datainput section 102.

Next, the operation of the present embodiment 15 will be described.

FIG. 33 is a flowchart illustrating the update data recording operationinto the update data recording section 3201 of the embodiment 15, andFIG. 34 is a flowchart illustrating the update operation of the map databy the dynamic update section 104 of the embodiment 15.

Referring to the flowcharts of FIGS. 33 and 34, the operation will bedescribed.

First, the recording operation of the update data into the update datarecording section 3201 will be described with reference to the flowchartof FIG. 33. The control section 108 acquires the update data from theupdate data input section 102 at a timing different from the timing of anavigation operation at step ST3301, and records the update data in theupdate data recording section 3201 at step ST3302. Subsequently, thecontrol section 108 makes a decision as to whether all the update datahave been input or not at step ST3303. If the input has been completed,the control section 108 terminates the processing, and otherwise itrepeats the processing from step ST3301.

Next, the operation of the dynamic update section 104 will be describedwith reference to the flowchart of FIG. 34. In response to a request formap data from an application at step ST3401, the dynamic update section104 reads the appropriate map data from the map data storing section 101at step ST3402. Then, the dynamic update section 104 reads the updatedata corresponding to the read map data from the update data recordingsection 3201 at step ST3403, followed by updating the map at stepST3404.

Thus, the present embodiment 15 updates the map in accordance with theupdate data recorded in the update data recording section 3201.Therefore it is not necessary to input the update data from the updatedata input section 102 during the navigation operation. This makes itpossible to use the update data input section 102 for other purposesduring the navigation operation. For example, when the update data inputsection 102 is a DVD, it can carry out DVD video replay during thenavigation operation. When the update data input section 102 is a memorycard, it is applicable to other navigation data exchange.

Furthermore, the speed-up of the map update itself can be expected byusing a high-speed medium such as a hard disk as the update datarecording section 3201.

Although the foregoing description is made assuming that the update datarecording section 3201 is installed separately from the map data storingsection 101, they may be incorporated into the same medium. For example,the same hard disk can record the map data and the update data.

As described above, the present embodiment 15 offers an advantage ofbeing able to provide a map data processing unit capable of using theupdate data input section 102 for other purposes during the navigationoperation by recording the update data into the update data recordingsection 3201 at a timing different from the navigation operation period.

1-13. (canceled)
 14. A map data processing unit comprising: an updatedata input section for inputting update data for updating old versionmap data to latest version map data; an update data recording sectionfor recording the update data input by said update data input section;an update section for updating, when a map data request from anapplication occurs, the old version map data to the latest version mapdata in accordance with the old version map data and the update datastored in said update data recording section, which old version map dataand update data correspond to the map data associated with the map datarequest from the application; a map data storing section for storing themap data; a display section for displaying a processing result of themap data; a manipulation section for performing input manipulation forprocessing the map data; and a control section for carrying out overallcontrol.